Updates to migration backends #750
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
LaurentRDC
reviewed
Mar 6, 2025
|
That is a very good idea. At work we use |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After several years, I've finally started working on a tool for beam migrations. I'll start a new repository for my tool, but there are some pieces missing from upstream beam that would be necessary for any migrations tool.
The key change here is adding a function to each backend to execute arbitrary SQL. This is necessary for any tool that allows running arbitrary migration scripts stored as backend-specific SQL.
The other major change is proper support for backend-agnostic transactions and proper connection handling.
All these changes are necessary for any migrations frontend, not just my tool.